Send feedback on this topic.

The ASP.NET configuration system features an extensible infrastructure that defines configuration settings at the time the ASP.NET application is first deployed, and allows administrators to add or revise configuration settings at any time with minimal impact on operational Web applications and servers.

The ASP.NET configuration system provides the following benefits:

• Configuration information is stored in XML-based text files. Any standard text editor or XML parser can be used to create and edit ASP.NET configuration files.
• Multiple configuration files, all named Web.config, can appear in multiple directories on an ASP.NET Web application server. Each Web.config file applies configuration settings to its own directory and all child directories below it. Configuration files in child directories can supply configuration information in addition to that inherited from parent directories, and the child directory configuration settings can override or modify settings defined in parent directories. The machine configuration file provides ASP.NET configuration settings for the entire server.
• At run time, ASP.NET uses the configuration information provided by the Web.config files in a hierarchical directory structure to compute a collection of configuration settings for each unique URL resource. The resulting configuration settings are then cached for all subsequent requests to a resource.
• ASP.NET detects changes to configuration files and automatically applies new configuration settings to Web resources affected by the changes. The server does not have to be rebooted for the changes to take effect. Hierarchical configuration settings are automatically recalculated and recached whenever a configuration file in the hierarchy is changed.
• The ASP.NET configuration system is extensible. You can define new configuration parameters and write configuration section handlers to process them.
• ASP.NET protects configuration files from outside access by configuring Internet Information Services (IIS) to prevent direct browser access to configuration files. HTTP access error 403 (forbidden) is returned to any browser attempting to directly request a configuration file.

See Also

See the following topics in the .NET Framework SDK documentation: Format of ASP.NET Configuration Files, ASP.NET Configuration.